Path: tosspot!indep1!pete From: pete@indep1.UUCP (Peter Franks) Newsgroups: to.tosspot Subject: TCP Digest #132 Message-ID: <1333@indep1.UUCP> Date: 14 Sep 90 01:21:48 GMT Reply-To: pete@indep1.MCS.COM (Peter Franks) Followup-To: to.tosspot Distribution: to Organization: as little as possible Lines: 140 TCP-Group Digest Fri, 7 Sep 90 Volume 90 : Issue 132 Today's Topics: *** LINKED to Forth / RTX-2000 help needed. RSPF data rspf info SLIP to Esix Rev D? Send Replies or notes for publication to: Send requests of an administrative nature (addition to, deletion from the distribution list, et al) to: Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". ---------------------------------------------------------------------- Date: Thu, 6 Sep 90 12:44:17 GMT From: toth!dave (David B. Toth) Subject: *** LINKED to To: tcp-group@ucsd.edu Contrary to some comments, RLI does not barf on this ... And Bill's comments are correct - some folks have screwed up on the spec ... Leave it in the BBS/Gateway code ... we'll get some of the other s/w writers to fix their code. 73, Dave VE3GYQ (@ VE3GYQ) ria.ccs.uwo.ca!toth!dave ------------------------------ Date: Thu, 6 Sep 90 10:48:14 EDT From: crompton@NADC.NADC.NAVY.MIL (D. Crompton) Subject: Forth / RTX-2000 help needed. To: idacrd!mac@uunet.UU.NET, tcp-group@ucsd.edu Bob, I spoke with our resident FORTH guru and he said that he would be glad to speak with you. He has done considerable RTX work and has alot of experience in FORTH. In talking with him he mentioned the RTX-2010, which should be out in the next year. This baby is specifically geared to the DSP community. Beta version may be around now or soon. Jim can fill you in more on this. So don't hesitate to contact him. He is alittle hard to get ahold of on the phone. Keep trying! His address and phone is: Jim Davidson Code 5051 Naval Air Developement Center Warminster, PA 18974 215-441-2573 - 215-441-3961 (LAB) The lab number may be better, but his desk number may forward to the lab anyhow. Let me know if you have problems getting him. He may be very helpful to you. He IS a real FORTH guru! Goes to all the conferences, knows Chuck Moore etc. 73 Doug ------------------------------ Date: Thu, 6 Sep 90 10:51:34 EDT From: crompton@NADC.NADC.NAVY.MIL (D. Crompton) Subject: RSPF data To: tcp-group@ucsd.edu Since it is not part of the nos userref manual (at least not the version I have) is there any info on RSPF and the implementation in G1EMM nos? Doug ------------------------------ Date: Thu, 06 Sep 90 16:43:04 GMT From: kelvin@kelvin.uk22.bull.com Subject: rspf info To: tcp-group@ucsd.edu Doug, I am putting up the docs I have on rspf to thumper. This consists of Freds definition and a mail message (edited) from Anders. Look in the thumper incoming dir. Hope this helps. All the best, Kelvin. +-------------------------------------------------+ | Kelvin J.Hill - BULL HN Ltd, Hounslow, England. | | Internet - kelvin.uk22.bull.com [128.35.110.6] | | Amprnet - g1emm.ampr.org [44.131.7.6] | +-------------------------------------------------+ ------------------------------ Date: Thu, 6 Sep 90 06:49:49 PDT From: "Image Systems Engineering, DTN264-1342, MKO2-2/K03 06-Sep-1990 0927" Subject: SLIP to Esix Rev D? To: tcp-group@ucsd.edu Has anyone had any experience running SLIP between NOS and a system running the Esix version (Rev D) of SYSV? The link comes up, but FTP's only seem to work doing a GET on the NOS system (i.e. transfer from Esix to NOS) The NOS is ??0490 version of G1EMM that I've ported to an AT&T Unix-PC. A couple things I've noticed when doing a PUT from NOS: If I set the MTU to what Esix is using (1024), then NOS appears to send the first block of data piggybacked with the last part of the handshake opening the data connection. As a result this segment gets fragmented at the IP level (because the MSS field makes the header longer?). Esix seems to never see (or never reassemble) this packet, so no data gets transferred. Am I interpreting this correctly (re the packet getting fragmented)? If I set the MTU smaller (256), then data flows, but with lots of retransmissions. Watching the trace, it looks like the Esix side is acknowledging packets as soon as they get there, by which time the NOS side usually has sent one or two more (the Esix side has a window of 2048). ------------------------------ Date: (null) From: (null) Anyone have any advice or other experience with NOS to 386 ix's? /gary K8LT grebus@nobozo.enet.dec.com ------------------------------ End of TCP-Group Digest ****************************** -- +------------------------------------------------------------------------------+ | Peter Franks | pete@indep1.mcs.com OR pete@indep1.uucp | | NI9D | Use whichever one works | +------------------------------------------------------------------------------+